Hi,
for a project I need to make a distinction between data definition language concepts and data manipulation language concepts which is common using standard SQL and relational databases. I mean: Something like DXL commands for just creating Modules, Types and Attributes etc... on the one hand and creating commands for filling such information structure with data on the other hand.
Question:
Is there already a functiopnality in DXL or does someone already implemented a functionality to "rigth click" on a DOORS module and finally getting the DXL creation commands for that DOORS module?
I think, that would be better instead of manualy creating the information structure directly using the graphical DOORS client and afterwards making a copy or archived export of that module in case of need for reusing exactly the same structure somewhere else, because in case of already having data whitin that module, I have to manually delete that data in the copied or imported module as postprocessing. But than, I would never get a so called new virgin DOORS module having just the information structure but no data or history, statistic entries etc....
Many thanks in advance, Helko
Helko - Thu May 05 05:41:26 EDT 2011 |
|
Re: Functionality for exporting an existing Module as DXL Script
Mathias Mamsch - Fri May 06 04:35:12 EDT 2011
Its not practicable to create a DXL script that will create another DXL script that will create a module for you. It is much more practiable to create a DXL script that will create a module from a XML source and another one that will make an XML Source for you. Creating DXL code on the fly is a little awkward and very hard to maintain and extend. And I guess there are several solutions for creating modules from a secondary source out there, like in the Rational Requirement Framework or even for starters the Project Startup Wizard of DOORS.
Regards, Mathias
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
|
|
Re: Functionality for exporting an existing Module as DXL Script
Mathias Mamsch - Fri May 06 04:41:20 EDT 2011
Regarding the DOORS module templates: Module Templates are indeed a way to go, but they don't help you with updating them and all the derived modules in the database. So ususually you would need another script for that. if you want a 'fresh' template you can always copy your module using the "Copy Special" function of DOORS which will give you a new module starting at Baseline 0.0 current, which only has the history of creating the objects. So this is basically what you would get if you had a script to create your module from another source. To get rid of the history draw a baseline 0.0 (empty suffix) and copy paste the module again.
Regards, Mathias
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
|
|
Re: Functionality for exporting an existing Module as DXL Script
Helko - Fri May 06 14:49:45 EDT 2011 Mathias Mamsch - Fri May 06 04:35:12 EDT 2011
Its not practicable to create a DXL script that will create another DXL script that will create a module for you. It is much more practiable to create a DXL script that will create a module from a XML source and another one that will make an XML Source for you. Creating DXL code on the fly is a little awkward and very hard to maintain and extend. And I guess there are several solutions for creating modules from a secondary source out there, like in the Rational Requirement Framework or even for starters the Project Startup Wizard of DOORS.
Regards, Mathias
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
The way using xml as intermediate storage is good. I've already implemented such functionality (storing DOORS (Meta)-Data as XML conform to a DOORS MetaModel and also creating DOORS (Meta)-Data based on such a XML File). The problem is, that this implemented functionality is tidely coupled with more coarse grained use case functionalities and it is complex to decouple the sub functionalities for the use cases I have right now. But I will have a look at it. The second problem (of course this is not a heavy problem) is that the end users need the MSXML library installed on their windows machines. But I'm also thinking that MSXML should be installed on nearly 100 % of windows machines world wide...
Best regards, helko
|
|
Re: Functionality for exporting an existing Module as DXL Script
Helko - Sat May 07 06:29:50 EDT 2011 Mathias Mamsch - Fri May 06 04:41:20 EDT 2011
Regarding the DOORS module templates: Module Templates are indeed a way to go, but they don't help you with updating them and all the derived modules in the database. So ususually you would need another script for that. if you want a 'fresh' template you can always copy your module using the "Copy Special" function of DOORS which will give you a new module starting at Baseline 0.0 current, which only has the history of creating the objects. So this is basically what you would get if you had a script to create your module from another source. To get rid of the history draw a baseline 0.0 (empty suffix) and copy paste the module again.
Regards, Mathias
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
another question:
You said, that the so called "Copy Special" function would be appropriate for using Module templates in DOORS. I cannot find this "Copy Special" function whithin the DOORS 8.1 Client. Is this function new to higher versions of DOORS?
Another question:
Do you now about something like an already existing UML profile for the DOORS Metamodel, so that a person might have the possibility to e.g. use such UML profile whith tools like Enterprise Architect to model the information structure of DOORS (Modules, Attributes, Types, Views, Columns, Folders etc...)? And in addition using an add on that takes such sterotyped UML model (xmi file) to automatically generate the information structure within the DOORS database? That would be nice, because than you would have something like model based DOORS engineering.
Regards, Helko
|
|
Re: Functionality for exporting an existing Module as DXL Script
Mathias Mamsch - Sat May 07 07:47:29 EDT 2011 Helko - Sat May 07 06:29:50 EDT 2011
Hi Mathias, others,
another question:
You said, that the so called "Copy Special" function would be appropriate for using Module templates in DOORS. I cannot find this "Copy Special" function whithin the DOORS 8.1 Client. Is this function new to higher versions of DOORS?
Another question:
Do you now about something like an already existing UML profile for the DOORS Metamodel, so that a person might have the possibility to e.g. use such UML profile whith tools like Enterprise Architect to model the information structure of DOORS (Modules, Attributes, Types, Views, Columns, Folders etc...)? And in addition using an add on that takes such sterotyped UML model (xmi file) to automatically generate the information structure within the DOORS database? That would be nice, because than you would have something like model based DOORS engineering.
Regards, Helko
The Copy Special function is available from the context menu of the modules in the database explorer. Do a right click, choose "Copy", then right click again and choose "Paste Special". For baselines you can use the "Copy Baseline" from the module menu which will do the same. If you want to keep absolute numbers, then in the telelogic kitchen tools is a script which will copy a module with absolute numbers intact.
Regards, Mathias
Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS
|
|